Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by keeper.albany.net (8.7.1/8.7.1) with ESMTP id BAA06460 for <dwarner@albany.net>; Fri, 15 Dec 1995 01:31:46 -0500 (EST)
Received: from garcia.com by relay2.UU.NET with SMTP
id QQzuei06349; Fri, 15 Dec 1995 01:13:20 -0500 (EST)
Received: from (localhost) by garcia.com (5.x/SMI-SVR4)
id AA10069; Fri, 15 Dec 1995 01:13:28 -0500
Date: Fri, 15 Dec 1995 01:13:28 -0500
Errors-To: dwarner@albany.net
Message-Id: <199512150446.VAA23160@earth.usa.net>
Errors-To: dwarner@albany.net
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: James Jones/Nibbles and Bits <jgjones@usa.net>
To: Multiple recipients of list <lightwave@garcia.com>
Subject: Another important tip for morphing projects
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
Adamchry@cats.ucsc.edu said:
>Okay, wavers...remember to parent all your morph targets to the first
>object of the morph chain. THen if you need to change teh objects
>position, starting rotation..etc..all teh objects will still be aligned...
Hate to disagree with you, but the position (in Layout space) of morph
target objects has no bearing on the morphing process. It does not matter
if the morph target is aligned with the source object -- it could be 100 km
away down the -Z axis and flipped upside-down and sized inside-out -- it
makes no difference.
The only position data for morphing that's important is from Modeler.
And morph targets don't need to be parented to anything. All they have
